翻訳と辞書
Words near each other
・ Backdrop
・ Backdrop Peak
・ Backdrop Ridge
・ Backe
・ Backe (surname)
・ Backe, backe Kuchen
・ Backe, Carmarthenshire
・ Backe, Sweden
・ Backen
・ Backen Church
・ Backer
・ Backer Aloenouvo
・ Backer Islands
・ Backergunge District
・ Back-chaining
Back-end database
・ Back-face culling
・ Back-fire
・ Back-formation
・ Back-Fusion
・ Back-illuminated sensor
・ Back-of-the-envelope calculation
・ Back-off pattern
・ Back-On
・ Back-pass rule
・ Back-rank checkmate
・ Back-reaction
・ Back-released velar click
・ Back-Room Boy
・ Back-seat driver


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Back-end database : ウィキペディア英語版
Back-end database

A back-end database is a database that is accessed by users indirectly through an external application rather than by application programming stored within the database itself or by low level manipulation of the data (e.g. through SQL commands).
A back-end database stores data but does not include end-user application elements such as stored queries, forms, macros or reports.
== Small database systems ==
The term back-end database is most widely used among developers using small database programming systems which can contain the end-user application programming within the database as a single item. The most common of these is Microsoft Access.
The developer must decide whether to include the application programming with the data in a single database, or whether to separate them into two database files, according to the client–server model.
For simple database applications, it is common for all programming to be stored with the data. This results in a single file and is easier to develop at the expense of scalability and concurrency.mb
For more advanced database applications it is common to split the data and the programming parts into a ''front-end database'' and a back-end database where the front-end holds all the application programming. This has advantages in terms of scalability, performance and concurrency but requires greater effort on the part of the developer. In the long term it may be easier to maintain and upgrade as new versions of the front-end can be deployed independently of the back-end database. The front and back-end databases do not always have to be of the same types. For example, it is possible to use a Microsoft Access front-end with a Microsoft SQL Server back-end.
It is common for developers to find that an existing database application has grown in complexity or usage to the point where it would have been better to have used separate front and back-end databases. Microsoft Access provides a ''Database Splitter Wizard'' to ease the process of splitting Access databases.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Back-end database」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.